Received: by mail3.netcom.com (8.6.8.1/Netcom) id XAA17928; Thu, 4 Aug 1994 23:18:24 -0700
Received: from nova.unix.portal.com by mail3.netcom.com (8.6.9/Netcom) id XAA17919; Thu, 4 Aug 1994 23:18:13 -0700
From: Jeric@cup.portal.com
Received: from hobo.corp.portal.com (hobo.corp.portal.com [156.151.1.14]) by nova.unix.portal.com (8.6.7/8.6.4) with ESMTP id XAA12549 for <lightwave-l@netcom.com>; Thu, 4 Aug 1994 23:17:34 -0700
Received: from localhost (pccop@localhost) by hobo.corp.portal.com (8.6.4/1.58) id XAA18989 for lightwave-l@netcom.com; Thu, 4 Aug 1994 23:17:31 -0700
To: lightwave-l@netcom.com
Subject: Re: Roto in Lightwave
Lines: 34
Date: Thu, 4 Aug 94 23:17:31 PDT
Message-ID: <9408042317.2.17553@cup.portal.com>
X-Origin: The Portal System (TM)
Sender: owner-lightwave-l@netcom.com
Precedence: list
Reply-To: lightwave-l@netcom.com
>I received a note stating that rotoing using lightwaves image sequence is not
>very accurate, that the images do not match the final frames, maybe some kind
>of scaling of the image when it is loaded in.
Hmmmmm, how are we using the term "rotoscoping" here? In my lexicon
it means, essentially, "tracing from captured imagery". In the 3D
world I take it to mean more like "positioning with captured imagery".
Or are you guys taping dancers and matching HUMANOID (great package)
with the captures?
If there is a consistant offset with the 1bit preview, Allen needs to
know ASAP.
>>>>>>>>>>>
OBTW, I just finished a project where we did 2d rotoscoping. Maybe
my methodology was wrong, but it was VERY laborious. Much more
so than I expected.
Hard-won advice: reduce your image to the GREATEST number of colors
(bitplanes) you can work with. Accelerated AGA machines are really the
way to go here.
Also, shoot the capture on the highest contrast background possible,
even if it means a lot of work. You'll thank me later.